Sams Teach Yourself MCSE Windows NT Server 4 in 14 Days
(Publisher: Macmillan Computer Publishing)
Author(s): David Schaer, et al
ISBN: 0672311283
Publication Date: 12/15/97

You normally begin local installation by booting from the NT Server Setup Disk 1. This initializes a basic version of NT, which loads the drivers necessary to access hardware including the CD-ROM drive. Figure 3.3 shows the installation at the point of initializing SCSI and IDE controllers.

If NT does not support the local CD-ROM drive it can still be used as a local source for the NT server installation files. An unsupported CD-ROM that is accessible under DOS can be treated as a network device for installation purposes. The installer would activate the CD-ROM under DOS and follow the directions for an over-the-network installation.

When dealing with a non-supported CD-ROM, you can copy the installation files to the hard drive and install from there.

Local installation is the only option for RISC machines. You must install them by using a supported SCSI CD-ROM. RISC machines boot from firmware and do not require the NT Server Setup disks.

Figure 3.3.  Local setup initializing SCSI and IDE controllers.

3.5.2. Initiating NT Server 4.0 Setup from a Network Share Point

Over-the-network setup from a share point on the server allows the system administrator to centrally control the installation files. The SA can either share the appropriate directory (such as I386) on the NT CD-ROM or copy the source files to a shared directory on the server.

The target machine must be connected to the file server via the network. If the operating system on the target machine is DOS-based, the executable will be WINNT.EXE. If the target machine is installed with an existing copy of NT, then WINNT32.EXE can be utilized.

WINNT.EXE and WINNT32.EXE

You can use both WINNT.EXE and WINNT32.EXE to perform either local or over-the-network installations.

After executing the file appropriate to the client’s operating system, the installation copies source files to a partition on the target computer. The basic installation creates a temporary directory called $WIN_NT$.~LS to hold the source files. If the /b option is used with WINNT.EXE or WINNT32 an additional directory, $WIN_NT$.~BT also is created.

This directory provides temporary storage for the information normally held on the three setup floppies. Because the /b option alleviates the need for the floppy disks, it is a common option to choose.

Other common switches to use with WINNT.EXE and WINNT32.EXE are as follows:

Figure 3.4.  The entry screen for the Setup Manager.

The unattended script file is a text file that provides the answers to the common setup questions. The system administrator controls the degree of user interaction.

After executing WINNT.EXE or WINNT32.EXE the initial files are copied to the temporary directories as described earlier. As the final step of phase one the system is rebooted.

Phase Two of NT Server 4.0 Setup

The installation setup screen is shown in Figure 3.5.

Figure 3.5.  The installation welcome screen.

Using the unattended script files as described previously would alleviate you from needing to respond to some or all of the screens that follow.

As seen in Figure 3.6, you have the option of specifying SCSI or IDE devices that are not detected automatically.

Figure 3.6.  You can select additional SCSI or IDE devices.

The license agreement is then displayed. You must agree to the license agreement to continue installation.

A screen appears, as shown in Figure 3.7, showing the hardware believed to be present in the system. You can override the hardware detected by the installation program. You must confirm the hardware before continuing.

Figure 3.7.  You are required to confirm detected hardware.